<!DOCTYPE html>
<html>
<head>
    <meta content="width=device-width,initial-scale=1" name="viewport">
    <meta name="Keywords" content="HTTP/2, HTTP/2.0, H2, Akamai, Cloud Computing, CDN, Mobile Experience, Content Delivery, Application Acceleration, Application Performance Management">
    <title>HTTP/2: the Future of the Internet | Akamai</title>
    <link href="./resources/h2.css" rel="stylesheet">
    <link href="./resources/push.css" rel="stylesheet">
    <link href="./resources/http5.css" rel="stylesheet">
    <link href="ds-aksb-a.akamaihd.net" rel="dns-prefetch">
    <link href="https://ds-aksb-a.akamaihd.net" rel="preconnect" crossorigin>

    <script>var w=window;if(w.performance||w.mozPerformance||w.msPerformance||w.webkitPerformance){var d=document;AKSB=w.AKSB||{},AKSB.q=AKSB.q||[],AKSB.mark=AKSB.mark||function(e,_){AKSB.q.push(["mark",e,_||(new Date).getTime()])},AKSB.measure=AKSB.measure||function(e,_,t){AKSB.q.push(["measure",e,_,t||(new Date).getTime()])},AKSB.done=AKSB.done||function(e){AKSB.q.push(["done",e])},AKSB.mark("firstbyte",(new Date).getTime()),AKSB.prof={custid:"359675",ustr:"",originlat:"0",clientrtt:"81",ghostip:"125.56.218.46",ipv6:false,pct:"10",clientip:"106.46.169.103",requestid:"2379676",region:"14008",protocol:"h2",blver:14,akM:"dscx",akN:"ae",akTT:"O",akTX:"1",akTI:"2379676",ai:"223318",ra:"false",pmgn:"",pmgi:"",pmp:"",qc:""},function(e){var _=d.createElement("script");_.async="async",_.src=e;var t=d.getElementsByTagName("script"),t=t[t.length-1];t.parentNode.insertBefore(_,t)}(("https:"===d.location.protocol?"https:":"http:")+"//ds-aksb-a.akamaihd.net/aksb.min.js")}</script>
</head>

<body>
<div id="wrapper">
    <div class="header-with-logo">
        <div class="container"><a href="http://www.akamai.com/"><img src="./resources/akamai-logo.png" /></a></div>
    </div>
    <div class="banner"><div class="banner-bg">
        <div class="container"><img alt="Akamai - HTTP2" src="./resources/http2-header.png" style="max-width:100%; height:auto"></div>
    </div></div>

    <div class="container"><div class="content">
        <div class="callout1" style="text-align: center;padding:5px 0px 5px 0px">
            <header><h2 class="highlight">

                You are using HTTP/2 right now! <span id="h2pushyes" class="yes"> (server-push is used)</span><span id="h2pushno" class="no"> (server-push is NOT used)</span><br/><button id="gobutton" type="submit" onclick="window.location = './demo';" autofocus>Click here for a DEMO</button>


            </h2>
            </header>
        </div>
        <div id="blurb">
            <header><h1>Turn-on HTTP/2 today!</h1></header>

            <p>HTTP/2<sup><a href="#fn1" id="ref1">[1]</a></sup> is real and available today with Akamai. <a title="Mark Nottingham talks about HTTP/2" href="https://www.mnot.net/blog/2015/02/18/http2">The standard was approved February 2015</a>, and <a title="HTTP/2 Web Browser support" href="http://caniuse.com/#search=http2">most of the leading browsers already support it</a>. Akamai customers can <a title="Enabling HTTP2 in Akamai" href="https://community.akamai.com/community/web-performance/blog/2015/01/26/enabling-http2-h2-in-akamai">enable it right now with a few clicks</a> without requiring any changes on the origin infrastructure.</p>

            <p><img alt="HTTP Timeline" src="resources/HTTP2-graphic.png" style="width:100%;height:auto"></p><strong>The web has dramatically evolved over the last 20+ years, yet HTTP - the
            workhorse of the Web - has not. Web developers have worked around HTTP's limitations, but:</strong>

            <ul>
                <li>Performance still falls short of full bandwidth utilization</li>

                <li>Web design and maintenance are more complex</li>

                <li>Resource consumption increases for client and server</li>

                <li>Cacheability of resources suffers</li>
            </ul>
            <strong>HTTP/2 attempts to solve many of the shortcomings and inflexibilities of HTTP/1.1.<br/>
                <br/>Its many benefits include:</strong>

            <ul>
                <li><strong> <a title="HTTP1.1 vs HTTP2 Demo" href="https://http2.akamai.com/demo">Multiplexing and concurrency</a>:</strong> Several requests can be sent in rapid succession on the same TCP connection, and responses can be received out of order -
                    eliminating the need for multiple connections between the client and the server</li>

                <li><strong>Stream dependencies:</strong> the client can indicate to the server which of the resources are more important<br>
                    than the others</li>

                <li><strong>Header compression:</strong> HTTP header size is drastically reduced</li>

                <li><strong>Server push:</strong> The server can send resources the client has not yet requested</li>
            </ul>

            <p>You will not need to change your websites or applications to ensure they continue to work properly. Not only will your application code and HTTP APIs continue to work
                uninterrupted, but your application will also likely perform better and consume fewer resources on both client and server.</p>

            <p>As it becomes more prevalent, organizations looking to benefit from the performance and security features of HTTP/2 should start thinking about how they are invested to fully capitalize on these new capabilities.  Such considerations include:</p>

            <ul>
                <li><strong>Encrypting:</strong> Applications running over HTTP/2 are likely to experience improvements in performance over secure connections.  This is an important consideration for companies contemplating the move to TLS.</li>

                <li><strong>Optimizing the TCP layer:</strong> Applications should be designed with a TCP layer implemented to account for the switch from multiple TCP connections to a single long-lived one, especially when adjusting the congestion window in response to packet loss.</li>

                <li><strong>Undoing HTTP/1.1 best practices:</strong> Many "best practices" associated with applications delivered over HTTP/1.1 (such as domain sharding, image spriting, resource in-lining and concatenation) are not only unnecessary when delivering over HTTP/2, and in some cases may actually cause sub-optimizations.</li>

                <li><strong>Deciding what and when to push:</strong> Applications designed to take advantage of the new server push capabilities in HTTP/2 must be carefully designed to balance performance and utility.</li>
            </ul>

            <p>Akamai can help and is working hard to address these and additional challenges, including possibly the toughest one: optimizing differently for HTTP/1.1 vs. HTTP/2 connections as
                browsers and other clients gradually transition over the next several years.</p>

            <p>HTTP/2 is available on Akamai to all customers using qualifying products to deliver TLS encrypted web content. Mark Nottingham chairs the IETF working group that defined the new standard - demonstrating our commitment to benefit users, content providers, service providers, developers and the Internet community at large</p>

            <p>It is important to note that Akamai and leading browsers intend to stop supporting SPDY when HTTP/2 is ready to take its place.</p>

            <p>For questions, please reach out to your Akamai representative, visit the <a title="Akamai Community Site" href="http://community.akamai.com/">Akamai&nbsp;Community</a> or <a href="http://www.akamai.com/html/forms/sales_form.html">click&nbsp;here</a> to contact us.</p>
        </div>

        <div id="additional">
            <div class="callout">
                <header><h2>Must Read</h2></header>
                <div style="text-align: center"><a href="http://amzn.to/2yarhth"><img src="./resources/learning_http2_cover_small.png"></div>
                <p>Learning HTTP/2 book, by Stephen Ludin and Javier Garza (March 31, 2016)</p></a>
            </div>
            <br/>
            <div class="callout">
                <header><h2>Insights from Experts</h2></header>

                <div style="text-align: center"><iframe width="100%" height="160" src="" data-src="https://www.youtube.com/embed/MARxcGRRTk4" frameborder="0" allowfullscreen></iframe></div>
                <p>Concur shares experience using H2 (March 31, 2016)</p>

                <div style="text-align: center"><iframe width="100%" height="160" src="" data-src="https://www.youtube.com/embed/HoAAkuZ3LoQ" frameborder="0" allowfullscreen></iframe></div>
                <p>Nespresso shares experience using H2 (March 15, 2016)</p>

                <div style="text-align: center"><iframe width="100%" height="160" src="" data-src="https://www.youtube.com/embed/4vnLUc58NEA" frameborder="0" allowfullscreen></iframe></div>
                <p>Akamai's Stephen Ludin on Internet evolution (February 10, 2016)</p>
            </div>
            <br/>
            <div class="callout">
                <header><h2>Additional Reading</h2></header>
                <p><a href="https://community.akamai.com/people/1-2GQWZ5/blog/2016/02/17/validate-certificate-h2-support-using-openssl">How to validate certificate h2 support using openssl&raquo;</a></p>

                <p><a href="https://community.akamai.com/people/1-2GQWZ5/blog/2016/02/17/http2-value-confirmation">HTTP/2 value confirmation using RUM&raquo;</a>

                <p><a href="https://blogs.akamai.com/2016/01/how-to-start-optimizing-in-an-h2-world.html">Stephen Ludin's blogpost about optimizing for both HTTP/1 and HTTP/2&raquo;</a></p>

                <p><a href="https://www.akamai.com/us/en/about/news/press/2015-press/akamai-helps-drive-adoption-of-http2-as-a-faster-and-more-secure-web-protocol.jsp">Akamai helps drive adoption of http/2&raquo;</a></p>

                <p><a href="https://blogs.akamai.com/2015/08/is-http2-worth-the-performance-price-of-tls.html">Stephen Ludin's blog: Is HTTP/2 worth the performance price of TLS?&raquo;</a></p>

                <p><a href="https://wcc.on24.com/webcast/previewlobby?e=1010864&k=225318383DA0846BED1DB09CCBB1148C">Webcast recording: HTTP/2 Uncovered: Top Tips for Successful Implementation. (By Richard Still from The Financial Times, and Michael Gooding from Akamai Technologies)&raquo;</a></p>

                <p><a href="https://blogs.akamai.com/2015/02/with-http2-akamai-introduces-next-gen-web.html">Stephen Ludin's post: With HTTP/2, Akamai Introduces Next Gen Web &raquo;</a></p>

                <p><a href="https://community.akamai.com/videos/1062">Mark Nottingham talks about HTTP/2&raquo;</a></p>

                <p><a href="https://www.mnot.net/blog/2014/01/30/http2_expectations">Mark Nottinghams' post: Nine Things to Expect from HTTP/2 &raquo;</a></p>

                <p><a href="http://http2.github.io/">HTTP/2 Page on GitHub &raquo;</a></p>
            </div><br/>

        </div>
        <div style="clear: both;"></div>
        <p><sup id="fn1">1. Formerly know as HTTP/2.0 or HTTP 2.0<a href="#ref1" title="Jump back to footnote 1 in the text.">&nbsp;&ldca;</a></sup></p>
    </div></div>
</div>
<!-- (javier) Performance Optimization: Defer loading the youtube video -->
<script>
    function init() {
        var vidDefer = document.getElementsByTagName('iframe');
        for (var i=0; i<vidDefer.length; i++) {
            if(vidDefer[i].getAttribute('data-src')) {
                vidDefer[i].setAttribute('src',vidDefer[i].getAttribute('data-src'));
            }
        }
    }
    window.onload = init;
</script>
</body>
</html>
